-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Support constants in custom storage layout expression #15944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
944dc30
to
059349f
Compare
4aae044
to
00ee32e
Compare
"The base slot of the storage layout must evaluate to an integer." | ||
); | ||
return; | ||
if (integerType->isSigned()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could also be removed from here and then replace the assert in line 173
as suggested in a previous PR #15528 (comment)
thank you for supporting constants! this is a huge composability unlock! |
Would this also apply to immutables? |
No, this only targets constants. Immutables are a little bit different and demand a different handling. |
We can't really support immutables here, because the layout must already be defined at creation time (constructor can initialize state variables), but their values can still change at that point. In case where they do not, the immutable can be replaced by a constant anyway. @matheusaaguiar Speaking of immutables, please make sure you have a test case against #15989. I.e. one showing that immutables are rejected even if they end up being treated as pure by the compiler. |
part of #15727.